Oracle Financial Services Compliance Regulatory Reporting Release
v8.1.2.7.0
|
Oracle Financial Services Compliance Regulatory Reporting Release
v8.1.2.7.0 |
Oracle Financial Services (OFS) Compliance
Regulatory Reporting (CRR) Pack is a
separately licensed product.
Description
Release ID 35193508 – OFS CRR 8.1.2.0.0 MINOR RELEASE #5
(8.1.2.7.0).
This release of OFS CRR is a cumulation of enhancements and
bug fixes since the 8.1.2.6.0 release. It is compatible with the 8.1.2.7.0 release
of Oracle Financial Services Enterprise Case Management (OFS ECM).
Prerequisites
Before applying OFS CRR v8.1.2.7.0, it is required to install
OFS CRR v8.1.2.0.0. For detailed instructions on installing this OFSCRR Release,
see OFSCRR Application Pack Installation Guide 8.1.2.0.0.
How to Apply This Patch?
For detailed
instructions on installing the OFS CRR 8.1.2.7.0 release, see the OFS CRR ML Installation
Guide.
About
This Release
This
section describes the new features, issues fixed, and known issues in this
release of OFS CRR.
Topics:
The following is the list of new features in this release:
US-SAR
· Generating
Correct/Amend Report: Once a SAR filing is finalized and the report status is
labeled as "Filed," CRR provides the capability to create a
Correct/Amend (C/A) report. Users can locate a "Generate C/A Report"
button on both the Report Details page and in the Report List section within
the E-File Status tab. On the Report Details page, users are empowered to
generate a correct/amend report for individual reports. It is crucial to
highlight that the functionality of the Generate C/A Report button is exclusive
to SDTM mode, and users can execute the C/A report process only once for a
Filed Report.
· Rejecting
Reports from an E-File: In SDTM
mode, when a rejected Message XML is submitted through batch upload, during the
parsing of the Message.xml, if the "Level" attribute has a value of
FATAL or WARN, the related reports in the corresponding E-File are
automatically flagged for rejection. This rejection status is recorded in the
Audit history for each affected report. Additionally, the associated rejected
Message XML is available for download from the Attachment column in the Audit
tab.
· Completing the
SAR Process: While performing Complete SAR Process Action, it is now
mandatory for the user to enter comments in the Comments dialog.
· Request for
Approval/Approve Report: When a CRR users request approval for a report or a
supervisor during the approval process, if the report size surpasses 60 MB, a
warning message is triggered: "The report contents exceeded the Efile size
limit. Please reduce report contents before proceeding further."
Consequently, users must take necessary actions before proceeding.
· Generating
E-File: In the Approved Report List section, if users choose
specific reports to generate an E-File and the resulting file size exceeds 60
MB, a warning message will be shown"The efile exceeds the size limit. To
automatically split the efile, click OK, or reduce the number of selected
reports before proceeding with the E-File generation.
· Report Context: Users can
now edit the Report Name in the Report Context section.
goAML
· Users can now configure the E-File name with Case ID and Report ID while
downloading an E-File.
Issues Fixed
The following is the list of bugs fixed in this release:
|
Bug No |
Component |
Resolution |
|
36337586 |
US-SAR |
On the Suspicious Activity Information tab, when users select any date in the Activity Date From date field (for example, 13-Sep-23) and save. The Application updates the previous date of the selected date. That is 12-Sep-23. This issue is resolved. |
|
US-SAR |
When users select the Report name in the Approved Reports list and click the Generate E-File button multiple times. The success message – “E-File generated Successfully” keeps popping up multiple times, and the report selected is also seen on the screen. This issue is resolved. |
|
|
US-SAR |
When the acknowledgment is uploaded using the SDTM process, duplicate entries appear on the acknowledgment list page. This issue is resolved. |
|
|
US-SAR |
When a user was working on Efile, other users could also work on the same approved report. The Approved Report has been made non-editable. This issue is resolved. |
|
|
US-SAR |
When SAR reports are migrated from 8.0.2.0.0 to the 8.1.2.0.0 version, the Type of Filing under Reporting Information is blank. This issue is resolved. |
|
|
US-SAR |
When users select the Form of identification as Unknown, the Audit tab has an entry for removal of identification. When users go to Subject Details, Another removed identification detail is added to the Audit history. This issue is resolved. |
|
|
US-SAR |
Under the Efile tab, the Reject button is not displayed when SDTM is enabled. This issue is resolved. |
|
|
US-SAR |
Approved reports are editable after selecting the Financial Institution where the activity occurred checkbox. This issue is resolved. |
|
|
CA-STR |
Even after entering all the mandatory information under Part C - Account information, the system was showing that the mandatory information was missing. This issue has resulted in reports not being approved (for all reports). This issue is resolved. |
|
|
US-SAR |
In SDTM Mode, the due date of the Case was based on Acknowledgement received from FINCEN. Now, the due date of the Case is based on when SAR is transmitted to FINCEN successfully. |
|
|
US-SAR |
In the Search page, the ‘Created by' drop-down was displaying only the users mapped to out-of-the-box SAR groups. This issue is resolved. |
|
|
US-SAR |
The Sort Ascending and Sort Descending buttons in the Report Number column of the Regulatory Reports module were reversed. If users sort ascending, the numbers go down, and if users sort descending, the numbers go up. |
|
|
36337603 |
US-SAR |
The jurisdiction drop-down showed all the values from DIM_DOMAIN tables even though users were not mapped to all the domains. This issue is resolved. |
|
US-SAR |
Users can set the due date to an older date than the current one. For example, users can set the due date as 1 January- 2023 as a due date already passed when the current date is 22-Feb-2024. This issue is resolved. |
|
|
US-SAR |
When a SAR report is created on a case and when users take actions like Approve, Reject, and Request for Approval actions on the SAR report, those details are not captured under Case audit. This issue is resolved. |
|
|
US-SAR |
Action Date field was not displayed under ‘31. Relationship With Financial Institution’ in the subject Information tab. This issue is resolved. |
|
|
goAML |
Removing functionality does not work for the phone grid under Account Entity Owner. This issue is resolved. |
|
|
US-SAR |
The Filing Type was not displaying correctly in the Report grid, and continueing activity report and joint report, filing type were displayed in the drop-down on the search page. This issue is resolved. |
|
|
US-SAR |
When users hover over Comment, it does not display the entire comment. This issue is resolved. |
|
|
US-SAR |
When the subject's address is marked as unknown, the corresponding tags were not created in the E-File. This issue is resolved. |
|
|
US-SAR |
When users try to take Close Filed action, then comments are not captured. The USER ID is displayed in the Comments column. This issue is resolved. |
|
|
US-SAR |
When users take action to reassign the report to other users, then the Action Taken By column in the Audit tab is updated as New Assigned user instead of a current user. |
|
|
US-SAR |
When users remove the Form of Identification in the Subject Information tab, duplicate entries are displayed in the Audit tab. This issue is resolved. |
|
|
GoAML |
In the Involved Account Details tab, two entries were displayed in the grid when users added existing director details. This issue is resolved. |
|
|
US-SAR |
When the number of reports is huge, the search with Date took longer. This issue is resolved. |
|
|
US-SAR |
In the Financial Institution Where Activity Occurred tab, the Branch page was allowing duplications. This issue is resolved. |
|
|
US-SAR |
Users had to perform close action twice to close the SAR report. This issue is resolved. |
|
|
US-SAR |
When users mistakenly paste an alphanumeric value such as case ID in the report name and click on search, The application hangs, and the application is not allowed to perform any actions. This issue is resolved. |
|
|
US-SAR |
There was a mismatch between the document count number in the regulatory report search screen and the documents attached in the document tab on the Report Details page. This issue is resolved. |
|
|
US-SAR |
The corresponding description is not displayed when users select the Other option in the Filining Institution. |
|
|
US-SAR |
Under the subject Information tab, when the Gender and Corroborative statement was blank, a user could not see any validation error. This issue is resolved. |
|
|
US-SAR |
When users search by the Report Name in the Efile status tab.The reports were not displayed. This issue is resolved. |
|
|
US-SAR |
The client was using two entities to file the CRR report. Hence, users must differentiate between these entities while generating the E-file. If users generated an E-file of two different entities together, then it was rejected by FinCEN. Hence, two new business domain fields are added to the Approved list grid. This issue is resolved. |
|
|
US-SAR |
In the Address grid, the Zip field was not allowed to add alphabets; it only allowed numbers. In the Netherlands, the zip code contains Alphabets. Hence, the Alphabet field is added. |
|
|
US-SAR |
When users try to generate a single efile for multiple reports with different TINs, users are able to generate an efile that is incorrect. This issue is resolved. |
There are no known issues in this release.
Oracle Financial Services Software Confidential
and Restricted | Copyright © 2023, Oracle and/or its affiliates.
All rights reserved. | Phone: +1.650.506.7000 | Fax: +1.650.506.7200 | www.oracle.com/industries/financial-services/index.html